Method and system for containment of usage of language interfaces

ABSTRACT

Client software is modified by a translator to use unique variant of linguistic interface of a service. An interceptor pre-processes subsequent client service requests from translated unique linguistic interface to standard linguistic interface implemented by service. Usage of linguistic interfaces of service is contained, rendering service incapable of executing arbitrary input, even if such input is crafted specifically for the service interface.

RELATED APPLICATION

This application is a divisional (and claims the benefit of priority under 35 U.S.C. §120 and §121) of U.S. application Ser. No. 10/739,230, filed Dec. 17, 2003, entitled “METHOD AND SYSTEM FOR CONTAINMENT OF USAGE OF LANGUAGE INTERFACES,” Inventor(s) Rosen Sharma, et al. The disclosure of the prior application is considered part of (and is incorporated by reference in) the disclosure of this application.

BACKGROUND

1. Field

Invention relates generally to computer systems, and in particular to controlling the use of computing resources by controlling language interfaces.

2. Related Art

Most information processing systems comprise hardware and software components with well-known interfaces, wherein the interfaces facilitate the use of the system components by other components specifically developed to use the interfaces. A common goal in practical computing comprises limiting the use of a specific system to software that the owners or operators of the system wish to use, disallowing the execution of arbitrary pieces of software on the system and the use of system resources by such arbitrary software, even if such software has been developed to use the interfaces provided by the system. However, this goal is difficult to achieve because of the impracticality of controlling the set of software that can attempt to execute on a given system. Furthermore, since the interfaces of most systems are well known, software with an opportunity to attempt execution or system usage will frequently succeed.

There are current techniques for limiting a given computing system such that only a specific set of software can execute on the system. Current techniques fall into the following categories: techniques for randomizing instruction sets; virtualization or mapping techniques; software encryption; and techniques for containing the use of functional interfaces and similar request-response interfaces including messaging interfaces. Encryption-based techniques rely on shared secrets used for cryptographic pre-execution checks, and fail to limit system usage once the pre-execution check succeeds. Randomized instruction set techniques generally rely on secret sharing schemes applied to functional interfaces, by using random secret data to transform a program's use of an interface's function names, keywords, instructions, command names, etc. Neither encryption or randomization has been used for programs that when executed compute or obtain new commands to execute. Virtualization avoids dependence on shared secrets but has been applied only to create variant name spaces for a fixed set of names of existing system resources such as memory addresses, file names, instruction operation codes, etc.

Accordingly, there is a need for a technique that is not based on validation checks, not limited by shared secrets, not limited to finite name space, and that applies to any linguistic representation and at all times, including cases where the running software computes or obtains new commands to execute.

SUMMARY

Present invention provides a method and system for containing the use of linguistic interfaces such that only a fixed set of software gains usage of a given system via a given linguistic interface. In one embodiment of the present invention, a translator modifies a body of software to use a unique variant of a linguistic interface, and an interceptor pre-processes subsequent invocations of the unique interface variant in order to re-translate the invocation to the standard language implemented by a standard system component. The interception and re-translation of service requests limits usage of the service to software that has been pre-translated to use the unique variant language.

The present invention can be used to contain the capabilities of any software comprising a linguistic interface (e.g. an interpreter, command shell, etc.), thereby rendering the software incapable of executing arbitrary input (e.g. directive, command, script, program) even if the input has been crafted specifically for that software's linguistic interface. Instead, in a contained system, an interpreter is capable of executing only a fixed set of input datasets or programs which are uniquely targeted at the individual system. Furthermore, the ability to create any additional uniquely targeted programs is a capability that is not present on the system.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating a system for containment of usage of language interfaces, according to an embodiment of the present invention.

FIG. 2 is a block diagram illustrating a system for containment of usage of language interfaces before the client program transformer and the service interface transformer are operational, according to an embodiment of the present invention.

FIG. 3 a is a flow chart illustrating the steps performed by the service interface transformer for the containment of usage of language interfaces, according to an embodiment of the present invention.

FIG. 3 b is a flow chart illustrating the steps performed by the client program transformer for the containment of usage of language interfaces, according to an embodiment of the present invention.

FIG. 3 c is a block diagram illustrating a system for the containment of usage of language interfaces after the client program transformer and the service interface transformer have performed the steps shown in FIGS. 3 a and 3 b.

FIG. 4 is a block diagram illustrating the result of the final step of the “build phase” in a system for the containment of usage of language interfaces, wherein the interceptor and the client program transformer are removed from the system, according to an embodiment of the present invention.

FIG. 5 is a block diagram illustrating the “run phase” of a system for the containment of usage of language interfaces, wherein one or more transformed clients use the service by interacting with the interceptor via the unique interface, according to an embodiment of the present invention.

FIG. 6 is a block diagram illustrating a system for the containment of usage of language interfaces, wherein an unknown program supplies some data to a unique client program, the data indicating an expression in the standard language, according to an embodiment of the present invention.

FIG. 7 a is a flow diagram illustrating a method for the containment of usage of language interfaces, according to an embodiment of the present invention.

FIG. 7 b is a block diagram illustrating an alternative embodiment of the present invention, wherein the service interface transformer transforms the service not by creating an interceptor for the service, but rather by modifying the service by replacing the standard language interface with a unique language interface.

FIG. 8 is a block diagram illustrating an alternative embodiment of the present invention, wherein the one or more clients and the service are on different hosts and communicate via a data network, according to an embodiment of the present invention.

FIG. 9 is a block diagram illustrating a similar network-based alternative embodiment of the present invention, using service modification or replacement similar to that shown in FIG. 7 b, according to an embodiment of the present invention.

FIG. 10 is a block diagram illustrating an alternative embodiment of the present invention, wherein the interceptor resides on a third host.

FIG. 11 is a block diagram illustrating an alternative embodiment of the present invention, wherein the interceptor resides on a component of the data network (such as a router or switch).

FIGS. 12 a and 12 b are state machine diagrams illustrating one embodiment of the present invention, according to an embodiment of the present invention.

FIG. 13 is a flow diagram illustrating the operation of the client program transformer, according to an embodiment of the present invention.

FIG. 14 is a flow diagram illustrating the operation of the client program transformer, according to an alternative embodiment of the present invention.

FIG. 15 is a flow diagram illustrating the operation of a variant procedure for initiating execution of a program, according to an embodiment of the present invention.

FIG. 16 is a flow diagram illustrating the operation of the client program transformer, according to an alternative embodiment of the present invention.

FIG. 17 is a flow diagram illustrating the operation of a variant procedure for initiating execution of a program, according to an embodiment of the present invention.

FIG. 18 is a flow diagram illustrating the steps of operation of the function UVOC, according to one embodiment of the present invention.

FIG. 19 is a flow diagram illustrating the steps of operation of the function COVU, according to an embodiment of the present invention.

FIG. 20 is a flow diagram illustrating the steps performed by the interceptor, according to an embodiment of the present invention.

DETAILED DESCRIPTION

The following serves as a glossary of terms as used herein:

Service interface (hereinafter also referred to as Linguistic Interface): An interface for use by a client of a service to submit a service request to an implementation of the service, wherein the client presents a dataset that conforms to a language specification (optionally expressed in terms of a grammar and a set of directives). A valid use of a linguistic interface comprises submitting (to the implementation of the interface) any of an infinite variety of linguistic statements that conform to the grammar of the language. This is in contrast to a functional interface comprising a finite number of distinct functions having one or more parameters of various kinds such that an instance of a valid use of the functional interface is a call to one of the functions with the correct kind of data items supplied for the function's parameters. A first linguistic interface is distinct from a second linguistic interface if the first linguistic interface comprises a grammar that is different from the grammar of the second linguistic interface, and/or if the first linguistic interface comprises a set of directives that is different from the set of directives of the second linguistic interface. A service interface is “standard” if it is disclosed publicly and/or is known as the primary interface of a service and/or is otherwise well-known.

Service: A specification of a behavior for implementing a functionality, comprising accepting a request and providing a response to the request according to the specified functionality. A service may optionally be specified in terms of existing resources and/or be defined in terms of other services.

Service Implementation: An implementation of a service, optionally embodied in a software interpreter, that consumes input comprising one or more directives and interprets the input in order to implement those directives by using services provided by hardware, or by other software running on a computer, or by software on other computers accessible via a data network. A first service implementation is equivalent to a second service implementation if for every service request the result of the interpretation of the first service implementation is the same as the result of the interpretation of the second service implementation (wherein the service requests are expressed in respective linguistic interfaces understood by the respective service implementations). In current practice, there are a variety of types of such interpreters; the present invention applies to any type of linguistic interpreter, including but not limited to the following:

-   -   Directives are expressed in a language designed for humans to         type system commands on a console. The interpreter is a program         called a command interpreter or command shell, while the input         is called a shell script or batch file.     -   Directives are expressed in a language designed for programming.         The interpreter is a program called an interpreter, while the         input is called a program; sometimes the terms script, and         scripting language are used.     -   Directives are executed by the interpreter by making direct use         of the resources of the local computer and the services of its         operating system, including OS services that enable the         interpreter to make use of other services either on the local         computer or on other computers accessible by a data network.     -   Directives are executed by the interpreter by means of executing         a compiler to convert the program into a binary program for the         local computer, and then executing the program on the local         computer, typically including either hardware, or         software-emulated hardware running on hardware. (This technique         is sometimes called just-in-time or JIT compilation.)     -   Directives are executed by the interpreter using a translator         for converting the program into a program in some other         language, and passing the translated program to an         implementation of that language.

Service Request: An expression in the language of a linguistic interface. An expression in a linguistic interface may comprise a constant data, the constant data representing a word and/or a literal in the linguistic interface. In the context of a first service implementation (accepting input according to a first linguistic interface) and an equivalent second service implementation (accepting input according to a second linguistic interface), a first service request expressed in the first linguistic interface is equivalent to a second service request expressed in the second linguistic interface if the result of the first service implementation on the first service request is the same as the result of the second service implementation on the second service request. If the first service request comprises a first constant data and the second service request (equivalent to the first service request) comprises a second constant data, such that the first constant data corresponds to the second constant data when considering the second service request as a translation of the first service request, then the first constant data is said to be equivalent to the second constant data (within the context of the two linguistic interfaces).

Service Parameter Data: A parameter in a service request, for passing to a service implementation. A service parameter data is a user input, a constant data, or a variable data, the variable data depending on a constant data or a user input via a code path in the program which generates the service request.

Client program: A program which makes use of a service using a linguistic interface. To do so, a client program formulates, and submits to the service implementation, a statement or expression (hereinafter also referred to as a “service request”) in the language of the interface. (It is important to note that two service requests may be equivalent, but be expressed in two different linguistic interfaces.) The service implementation processes the submitted statement or expression producing one or more results such as: returning output data that indicates successful execution; returning output data that is the result of successful execution; returning output describing unsuccessful execution. A client program may perform such a submission one or more times. When a given client program makes multiple submissions, the client program is typically gathering external input and formulating submissions that form part of its processing of the input. A very important typical case of a single submission comprises an entire program in the interpreted language submitted for execution via the interpreter.

FIG. 1 is a block diagram illustrating a system for containment of usage of language interfaces, according to an embodiment of the present invention. Computing system (CS) 11 comprises one or more client programs (CP) 21 of a given service, a client program transformer (CPT) 22, one or more unique client programs (UCP) 23, a service implementation SVC 24 implementing a service used by a CP 21, a service interface transformer (SIT) 25 and an interceptor (INTC) 26. The SVC 24 comprises a standard linguistic interface (SLI) 31 and a service implementation (SIMPL) 32. The interceptor INTC 26 comprises a unique linguistic interface (ULI) 33 and SVC 24. SLI 31 and ULI 33 are instances of a linguistic interface. SIMPL 32 is an instance of a service implementation. CP 21 and UCP 23 are instances of client programs of a service.

FIGS. 2 through 4 illustrate the first of two phases of the present invention, the first being the “build phase” and the second being the “run phase.” In the “build phase”, the client program transformer CPT 22 and the service interface transformer SIT 25 are actors, while the interceptor INTC 26 and the unique linguistic interface ULI 33 are results of actions performed by the actors, as are the transformed clients UCP 23.

FIG. 2 is a block diagram illustrating a system for containment of usage of language interfaces before the client program transformer CPT 22 and the service interface transformer SIT 25 are operational, according to an embodiment of the present invention. The standard implementation of the service SVC 24 and its one or more clients CP 21 are present on the system CS 11.

FIG. 3 a is a flow chart illustrating the steps performed by SIT 25 for the containment of usage of language interfaces, according to an embodiment of the present invention. SIT 25 generates 201 the unique linguistic interface ULI 33, analyzes 202 the service SVC 24 to determine how to install the interceptor INTC 26, and generates 203 and installs the interceptor to capture the input for SVC 24 and redirect it through ULI 33.

FIG. 3 b is a flow chart illustrating the steps performed by the transformer CPT 22 for the containment of usage of language interfaces, according to an embodiment of the present invention. Transformer CPT 22 analyzes 210 the one or more clients CP 21, and generates 211 one or more transformed clients UCP 23, wherein the transformed clients UCP 23 are functionally identical to the standard clients CP 21 but instead use the unique interface ULI 33 to interact with the service SVC 24.

FIG. 3 c is a block diagram illustrating a system for the containment of usage of language interfaces after the client program transformer CPT 22 and the service interface transformer SIT 25 have performed the steps shown in FIGS. 3 a and 3 b. Arrows indicate the analysis of the SVC 24 and the generation of the unique linguistic interface ULI 33 and the interceptor INTC 26 by the interface transformer SIT 25, as well as the analysis of the clients CP 21 and the generation of the transformed clients UCP 23 by the client transformer CPT 22.

FIG. 4 is a block diagram illustrating the result of the final step of the “build phase” in a system for the containment of usage of language interfaces, wherein the service interface transformer SIT 25 and the client program transformer CPT 22 are removed from the system CS 11, according to an embodiment of the present invention. The removal of the service interface transformer SIT 25 and client program transformer CPT 22 eliminates the ability for subsequent transformation of client programs CP 21 or re-generation of the interceptor INTC 26. The original client programs CP 21 may or may not be present; the unique clients UCP 23 are used instead.

FIG. 5 is a block diagram illustrating the “run phase” of a system for the containment of usage of language interfaces, wherein one or more transformed clients UCP 23 use the service SVC 24 by interacting with the interceptor INTC 26 via the unique interface ULI 33 (indicated by the arrow from UCP 23 to ULI 33), according to an embodiment of the present invention. As a result of the “build phase”, the only way to use the service SVC 24 is via interaction with the interceptor INTC 26. Because the transformed clients UCP 23 use the correct language interface ULI 33, the interceptor INTC 26 can interpret the clients' UCP 23 request and re-translate a unique-language expression into a standard-language expression and pass it to SVC 24 (indicated by the arrow from ULI 33 to SVC 24). The same interception process occurs for other attempts to use SVC 24, including attempts from an original client program CP 21, or from any other program (denoted UP 27) which is not part of the fixed set of unique clients generated in the “build phase” and which therefore does not use the unique language interface ULI 33. Nevertheless, such attempts are redirected to ULI 33 (indicated by arrow from UP 27 to ULI 33), and the interceptor INTC 26 will be unable to interpret the input data originating from such program UP 27 since such input data is not expressed in the unique language of ULI 33.

FIG. 6 is a block diagram illustrating a system for the containment of usage of language interfaces (similar to the system shown in FIG. 5), wherein an unknown program UP 27 supplies to a unique client UCP 23 data indicating an expression in the standard language, according to an embodiment of the present invention. Even if the unique client UCP 23 inadvertently passes on such a standard-language expression in a service request to SVC 24, the interceptor INTC 26 will be unable to interpret the standard-language expression.

FIG. 7 a is a flow diagram illustrating a method for the containment of usage of language interfaces, according to an embodiment of the present invention. FIG. 7 a shows the steps for the correct execution of only selected client programs present on the system CS 11 in the “build phase”, while rendering the system CS 11 incapable of providing service to any other (untransformed) clients (as described above in FIGS. 2 through 6):

-   -   Install 301 service interface transformer SIT 25 and         client-program-transformer CPT 22.     -   Run 302 SIT 25 and CPT 22 to create transformed clients UCP 23         which use a unique variant of the standard language, and an         interceptor INTC 26 that implements this language. (Details of         the operation of the client program transformer CPT 22 are         described below and shown in FIGS. 13 through 17).     -   Remove 303 the service interface transformer SIT 25 and         client-program-transformer CPT 22.     -   When a program attempts to use the service SVC 24, the         interceptor INTC 26 attempts to interpret the program's         submission as an expression in the unique variant of the         standard language. (Details of the operation of the interceptor         INTC 26 are described below and shown in FIG. 20).         -   If successful, the interpretation of the unique variant             results in an expression in the standard language, which is             passed to the standard service SVC 24.         -   If unsuccessful, then one of several possible error handling             options are used, including but not limited to the             following:             -   Do not call on the standard service SVC 24.             -   Do call on the standard service SVC 24, with the                 re-translated portions of the unique-language request,                 including any un-translated expressions by converting                 them into constant data in the standard language.             -   Do call on the standard service SVC 24, with the                 re-translated portions of the unique-language request,                 excluding any un-translated expressions.

FIG. 7 b is a block diagram illustrating an alternative embodiment of the present invention, wherein the SIT 25 transforms the service SVC 24 not by creating an interceptor INTC 26 for the service (as described above and indicated in FIG. 1), but rather by modifying SVC 24 by replacing the standard interface SLI 31 with ULI 33. In this embodiment the “run phase” differs in that no re-translation occurs since there is no longer any service that uses the standard interface. Any request not formulated in the unique language will not be interpreted successfully.

In another alternative embodiment of the present invention, the service SVC 24 is not modified, but rather replaced with a new service that is functionally equivalent to the standard service, but which uses the unique language as its interface ULI 33. Again, any request that is not formulated in the unique language will not be interpreted successfully.

FIG. 8 is a block diagram illustrating an alternative embodiment of the present invention, wherein the one or more clients and the service are on different hosts and communicate via a data network denoted DN 12. The client software is on the host denoted CS 11 while the service SVC 24 is on the host denoted SCS 13. This embodiment comprises an interceptor INTC 26 in a manner analogous to the embodiment described in FIG. 1. The dataflows between the components are transmitted over the network DN 12, but are otherwise as described above for FIGS. 2 through 6.

FIG. 9 is a block diagram illustrating a similar network-based alternative embodiment of the present invention, using service modification or replacement similar to that shown in FIG. 7 b. The dataflows between the components are transmitted over the network DN 12, but are otherwise as described above for FIG. 8.

FIG. 10 is a block diagram illustrating an alternative embodiment of the present invention, wherein the interceptor INTC 26 resides on a third host denoted ICS 14. The dataflows between the components are transmitted over the network DN 12, but are otherwise as described above for FIGS. 2 through 6. In the embodiment shown in FIG. 10, effective usage requires an ancillary mechanism for network-level access control, embodied in the network DN 12, that blocks direct communication from the host CS 11 to the host SCS 13 for the communication channels used by the service SVC 24.

FIG. 11 is a block diagram illustrating an alternative embodiment of the present invention, wherein the interceptor INTC 26 is on a component of the data network DN 12 (such as a router or switch) denoted DNE 15. The “run phase” dataflows are similar to those shown in FIG. 10, except that the interceptor INTC 26 is on the data network element DNE 15 rather than on a server host. The “build phase” dataflow differs in that the service interface transformer SIT 25 runs on host SCS 13 as in FIG. 8, but installs the interceptor INTC 26 on the data network element DNE 15 (indicated by the arrow from SIT 25 to INTC 26). In one embodiment, the interceptor INTC 26 is able to intercept because the data network element DNE 15 is in the physical communication path between the hosts CS 11 and SCS 13. In an alternative embodiment, the interception depends on network level routing and/or access controls for enforcing that communication between hosts CS 11 and SCS 13 passes through the data network element DNE 15.

It is an advantageous aspect of the present invention that the transformers SIT 25 and CPT 22 may run on any host and use the network to push the generated software (UCP 23, INTC 26 and ULI 33), comprising portable code, to one or more hosts on which the generated software will run. Furthermore, the build-hosts need not necessarily be network-connected, since the generated software can be moved to the run-hosts using movable storage such as CD-ROMS, diskettes, or any other storage media. Additionally, in this case, the build-hosts need not actually run the generated software. This allows the present invention to be deployed in a distributed computing environment, such as a client-server environment, a client-proxy-server environment, a client-DNE-server environment, and/or other distributed computing environment.

FIGS. 12 a and 12 b are state machine diagrams illustrating one embodiment of the present invention as operating on a single computing system, according to an embodiment of the present invention. FIG. 12 a shows a state machine for a service and FIG. 12 b shows a state machine for a client. A client can cause a state change in a service by sending a request to the service. A service can cause a state change in a client by replying to a client request. Other state changes are the result of the operation of components of the present invention.

The following list describes the states and state transitions shown in FIGS. 12 a and 12 b:

-   -   State: service initial state (SVI 401)—The system components         that implement a service are installed on the system upon which         the present invention will be used, and are capable of operating         in a normal manner to implement a standard or common linguistic         interface. For a given linguistic interface, there may be         multiple components, including separate independent instances of         services using the same linguistic interface. For a given         system, there may be multiple distinct linguistic interfaces         that can be contained.     -   State: client initial state (CLI 402)—for each instance of each         service using a linguistic interface, the initial state of the         client software is that it is installed on the system upon which         the present invention will be used, and is capable of operating         in a normal manner to use a standard or common linguistic         interface.     -   State: service unique state (SVU 403)—service implements only a         specific unique variant of the standard interface, for example,         by means of encapsulation by an interceptor, or by means of         direct modification or replacement of service implementation.     -   State: client unique state (CLU 404)—client uses only a specific         unique variant of the standard interface.     -   State transition: service solidification (SSFY 405)—starting         state is service initial state; ending state is service unique         state.     -   State transition: client solidification (CSFY 406)—starting         state is client initial state; ending state is client unique         state.     -   State: service unique receiving state (SVUR 407)—service         implements only a specific unique variant of the standard         interface, and is operational.     -   State transition: service unique execution (SUEXEC 408)—starting         state is service unique state; ending state is service unique         receiving state.     -   State: client unique operating state (CLUO 409)—client uses only         a specific unique variant of the standard interface, and is         operational.     -   State transition: client unique execution (CUEXEC 410)—starting         state is client unique state; ending state is client unique         operating state.     -   State: client unique sending state (CLUS 411)—client has made a         service request using the unique interface.     -   State transition: client unique request (CUREQ 412)—starting         state is client unique operating; ending state is client unique         sending.     -   State transition: unique request success (CUSUCC 413)—starting         state is client unique sending; ending state is client unique         operating; the client's request was successfully executed by the         service, and appropriate return data supplied to client.     -   State transition: unique request error (CUERR 414)—starting         state is client unique sending; ending state is client unique         operating; the client's request was not successfully executed by         the service, and appropriate error return data supplied to         client.     -   State: client standard operating state (CLSO 415)—client uses         standard interface, and is operational.     -   State transition: client standard execution (CSEXEC         416)—starting state is client initial state; ending state is         client standard operating state.     -   State: client standard sending state (CLSS 417)—client has made         a service request using the standard interface.     -   State transition: client standard request (CSREQ 418)—starting         state is client standard operating; ending state is client         standard sending.     -   State transition: standard request error (CSERR 419)—starting         state is client standard sending; ending state is client         standard operating; the client's request was not successfully         executed by the service, and error return data supplied to         client may indicate the service's inability to process the         request because it did not conform to the service's linguistic         interface.     -   State: service unique processing state (SVUP 420)—service         implements only a specific unique variant of the standard         interface, and is processing a request.     -   State transition: service unique reception (SURECV 421)—starting         state is service unique receiving state; ending state is service         unique processing state.     -   State transition: service unique request success (SUSUCC         422)—starting state is service unique processing state; ending         state is service unique receiving state; the client's request         was successfully executed by the service, and appropriate return         data is supplied to client.     -   State transition: service unique request error (SUERR         423)—starting state is service unique processing state; ending         state is service unique receiving state; the client's request         was not successfully executed by the service, and appropriate         error return data is supplied to client.     -   State transition: unsuccessful service solidification (SSFYERR         424)—starting state and ending state are both service initial         state; the attempt to solidify the service components         encountered an execution error.     -   State transition: unsuccessful client solidification (CSFYERR         425)—starting state and ending state are both client initial         state; the attempt to solidify a service's client encountered an         execution error.     -   State transition: unsuccessful unique service execution         (SUEXECERR 426)—starting state is service unique state; ending         state is service unique state; failure in attempt to execute         service implementation.     -   State transition: unsuccessful unique client execution         (CUEXECERR 427)—starting state is client unique state; ending         state is client unique state; failure in attempt to execute         client.     -   State transition: unsuccessful standard client execution         (CSEXECERR 428)—starting state is client initial state; ending         state is client initial state; failure in attempt to execute         standard client.

The components described in FIGS. 1 through 11 operate according to the state machines illustrated in FIGS. 12 a and 12 b. Client software CP 21 starts out in the initial state CLI 402, installed and capable of using the standard linguistic interface of a service SVC 24. The operation of the client program transformer CPT 22 on client software CP 21 constitutes either (a) the state transition CSFY 406 from state CLI 402 to state CLU 404, or (b) the state transition CSFYERR 425 from state CLI 402 to state CLI 402, in cases where the transformer CPT 22 is unable to complete its operation to create a unique client program UCP 23 that is functionally equivalent to the original client software but which uses a unique interface ULI 33.

A service implementation SVC 24 starts out in the initial state SVI 401, installed and offering the service via its standard linguistic interface SLI 31. The operation of the service interface transformer SIT 25 on a service implementation SVC 24 constitutes either (a) the state transition SSFY 405 from state SVI 401 to state SVU 403, or (b) the state transition SSFYERR 424 from state SVI 401 to state SVI 401, in cases where the service interface transformer SIT 25 is unable to complete its operation to create an interceptor for SVC 24 or to directly modify or replace SVC 24 so that it provides a functionally equivalent service via a unique interface ULI 33.

If the client program transformer CPT 22 is successful in converting designated client software CP 21 that uses a given service SVC 24, and if the service interface transformer SIT 25 is successful in transforming the service SVC 24, then the “build phase” is complete and the service has been contained. “Designated client software” in this context refers to one or more software packages that are selected (typically but not necessarily by a human operator) to be converted and hence enabled to successfully use the contained service. For example, the designated client software would be all client software of a given service that are installed on a given computing system.

Following this “build phase”, the converted service and clients can be executed using the capabilities of the computing system that they are installed on. Execution of the service SVC 24 constitutes either (a) the state transition SUEXEC 408 from state SVU 403 to state SVUR 407, or (b) the state transition SUEXECERR 426 from state SVU 403 to state SVU 403, in cases where the computing system is unable to successfully start execution of the service SVC 24. After state transition SUEXEC 408, the service SVC 24 is ready to receive service requests via the unique interface ULI 33.

Similarly, execution of the unique client program UCP 23 constitutes either (a) the state transition CUEXEC 410 from state CLU 404 to state CLUO 409, or (b) the state transition CUEXECERR 427 from state CLU 404 to state CLU 404, in cases where the computing system is unable to successfully start execution of the client UCP 23. After state transition CUEXEC 410, the transformed client UCP 23 is operating and may (depending on its input and course of execution) make one or more requests of the service SVC 24 via the unique interface ULI 33.

Following the “build phase” it is still possible for standard (i.e. untransformed) client software to run and attempt to use a contained service. Such standard client software comprises one or more clients CP 21 that remain installed after the “build phase”, or unknown programs (such as UP 27 shown in FIG. 5) that may have been introduced into the computing system CS 11 after the “build phase”. Execution of these programs constitutes either (a) the state transition CSEXEC 416 from state CLI 402 to state CLSO 415, or (b) the state transition CSEXECERR 428 from state CLI 402 to state CLI 402, in cases where the computing system is unable to successfully start execution of the client. After state transition CSEXEC 416, the client is in the standard (i.e. not unique) operating state CLSO 415 and may (depending on its input and course of execution) make one or more requests of the service SVC 24 via the standard interface SLI 31. Because the service can be used only via the unique interface ULI 33, such attempts fail, with such attempts and failure shown as a state transition CSREQ 418 from state CLSO 415 to state CLSS 417, which is constituted by the client software making a standard request of the service SVC 24 and waiting for the result. This eventually results in a further state transition CSERR 419 from state CLSS 417 to state CLSO 415, which is a result of the service SVC 24 returning an error due to the client failing to make a comprehensible service request via the unique interface ULI 33, the ULI 33 representing the only way that service SVC 24 may respond to a service request.

Successful use of the service by a client UCP 23 is shown in FIG. 12 b as a state transition CUREQ 412 from state CLUO 409 to state CLUS 411, which is constituted by the unique client software UCP 23 making a request of the service SVC 24 and waiting for a result. There are two possible further state transitions. In the first case, the client's UCP 23 request is successfully executed and the service returns appropriate output data to the client UCP 23, with the service's return causing a state transition CUSUCC 413 from state CLUS 411 back to state CLUO 409. In the second case, the service is unable to complete the client's UCP 23 request and returns appropriate error return data to the client UCP 23, with the service's return causing state transition CUERR 414 from state CLUS 411 back to state CLUO 409.

A similar success or error pair of state transitions applies to the service implementation SVC 24. When the service is in state SVUR 407 waiting for a request, a client request triggers the state transition SURECV 421 from state SVUR 407 to state SVUP 420, the state in which the service attempts to process the request. At this point, two further state transitions are possible, both from state SVUP 420 back to state SVUR 407. Transition SUSUCC 422 represents the case where the client request was successfully completed. Transition SUERR 423 represents the case where the client request was not successfully completed, for example because the client request was incomprehensible (i.e. not expressed according to the unique variant ULI 33 of the standard linguistic interface of the service SVC 24), or due to an execution error encountered while processing the client request despite the client request being linguistically correct.

The client program transformer CPT 22 operates by examining an input program (a client program CP 21) and producing an output program (a unique client program UCP 23). Three properties characterize the input and output programs:

-   -   The output program UCP 23 differs from the input program CP 21         in terms of the data used by the program to formulate         expressions in the language of the interface of the service         used.     -   In the input program CP 21, expression formulation includes the         use of constant data, for example a string representing a         keyword of the standard language.     -   In the output program UCP 23, expression formulation is based on         processing data to emit the unique variant language according to         ULI 33 instead of according to the standard language interface         SLI 31.

FIG. 13 is a flow diagram illustrating the operation of the client program transformer CPT 22, according to an embodiment of the present invention, wherein a “calling code sequence” is defined as a code sequence that submits one or more service parameter data to a service for interpretation, for example, a call of a function that passes its input data to the service that implements the standard language SLI 31, and wherein a “constant code sequence” is a code sequence in which constant data is used to compute service parameter data that is subsequently used as a standard language SLI 31 expression in a “calling code sequence.” The following describes the operation of the client program transformer CPT 22:

-   -   Scan the input program CP 21 and compile 501 a list of all the         “calling code sequences” for calls to the service that         implements the standard language SLI 31.     -   For each “calling code sequence” in the “calling code sequence”         list, scan the input program to compile 502 a list of all the         “constant code sequences” that use constant data to compute         service parameter data that is used in that “calling code         sequence” (an example “constant code sequence” is an expression         comprising a constant value, the result of the expression used         in a variable assignment, the variable in turn used in a         function call, the function call for passing data to a service         implementation).     -   For each “constant code sequence” in the “constant code         sequence” list, and for each constant value used in that         “constant code sequence,” define 503 a “substitution code”         comprising a call to a subroutine, the subroutine implementing         the function UVOC (described below), with the constant data         value as an argument to the subroutine call.     -   Create a copy of the input program, and modify 504 it as         follows:         -   For each “constant code sequence” in the “constant code             sequence” list, and for each constant value used in that             “constant code sequence,” replace the constant value with             the corresponding “substitution code” previously defined.     -   After all such substitutions have been applied, output 505 the         resulting modified input program.

As a result of the steps shown in FIG. 13, the output program is the same as the input program, except that selected uses of a constant value have been replaced by a call to the function UVOC on the same constant value. In addition, the output program also contains the implementation of the function UVOC, together with supporting code and data used by the function UVOC.

An important “degenerate case” of an input program is a program that entirely consists of one expression in the language of the interface of the service. The execution of this program comprises passing the program data to the interpreter implementing the service. The unique variant of this client program comprises passing to the interpreter the result of the function UVOC when provided with the input program in its entirety.

In the embodiment of the client transformer CPT 22 described above and shown in FIG. 13, the substitution (i.e. replacing selected uses of constant values with calls to UVOC using the replaced constant value) is performed during the “build phase” so that the unique client software is executed during the “run phase” using the normal services of the base computing system.

FIG. 14 is a flow diagram illustrating the operation of the client program transformer CPT 22, according to an alternative embodiment of the present invention. The terms “substitution” and “substitution definition” are defined as in the description of FIG. 13. In this embodiment, the “build phase” client-generation activities of the client program transformer CPT 22 are limited to the steps illustrated in FIG. 14 and described as follows:

-   -   Define 510 the substitutions for each client program as         described above and shown in FIG. 13, storing each program's         substitution definitions in a “unique programs list” for later         use during the “run phase.”     -   From the “unique programs list” data, compute 511 and store data         (such as a checksum) that can be used later for integrity checks         to detect modification of (a) the “unique programs list” data         and/or (b) a program's substitution definition and/or (c) a         program referenced in the “unique programs list”.     -   Modify the base computing system to implement 512 a variant of         the usual procedure for initiating execution of a program, which         variant procedure is described below and shown in FIG. 15.

During the “run phase,” the unique client UCP 23 is constructed as part of this variant procedure for initiating execution of a standard client CP 21. This variant procedure comprises the steps shown in FIG. 15 and is described as follows, wherein the terms “substitutions” and “substitution definition” are used in the same sense as in the above description of FIG. 13:

-   -   Determine 520 whether the program to be executed is in the         “unique programs list” for which there are stored substitutions.     -   If not 521, then execute 522 the program normally.     -   Otherwise 523, check 524 the integrity of the “unique programs         list” data.     -   If 525 modification of (a) the “unique programs list” data         or (b) the program's substitution definition or (c) the program         itself (as referenced in the “unique programs list”) is 526         detected, then do not execute 527 the program.     -   Otherwise 528, obtain the stored substitutions for the program         from the “unique programs list” and construct 529 a unique         client UCP 23 by performing the stored substitutions on the         program in the manner described in FIG. 13.     -   Instead of executing the original program, execute 530 the         unique client UCP 23.

Another embodiment is a variation on the embodiment shown in FIG. 15, wherein the “stored substitutions” for a given program comprise solely a substitution of the code of the unique client UCP 23 for the code of the client program CP 21. In other words, the unique client UCP 23 is generated during the “build phase” and stored for later use in the “run phase” during which, when there is a request to execute the standard client CP 21, the corresponding pre-defined unique client UCP 23 is executed instead.

FIG. 16 is a flow diagram illustrating the operation of the client program transformer CPT 22, according to an alternative embodiment of the present invention. In this embodiment, the “build phase” client-generation activities of the client program transformer CPT 22 are limited to the steps illustrated in FIG. 16 and described as follows:

-   -   Define 530 a manifest of client programs CP 21 that are         authorized to use the service.     -   For each such program, create 531 data (such as a checksum) that         can be used later for integrity checks to detect modification of         the program, and add that data to the manifest.     -   Store 532 this manifest for later use.     -   From the manifest data, create 533 and store data (such as a         checksum) that can be used later for integrity checks to detect         modification of the manifest data.     -   Modify the base computing system to implement 534 a variant of         the procedure for initiating execution of a program, which         variant procedure is defined below and shown in FIG. 17.

During the “run phase,” the unique client UCP 23 is constructed as part of this variant procedure of initiating execution of a standard client CP 21. FIG. 17 is a flow chart illustrating the steps of this variant procedure, according to an embodiment of the present invention. The terms “substitution” and “substitution definition” are used in the same sense as in the above description of FIG. 13.

-   -   Check 540 the integrity of the manifest. If modification is 541         detected, then do not execute 542 any program.     -   Otherwise 543, check 544 the manifest to see if it includes the         program to be executed.     -   If manifest does not include 545 the program to be executed,         then execute 546 the program normally.     -   Otherwise 547, check 548 the integrity of the program. If         modification is 549 detected, then do not 550 execute any         program.     -   Otherwise 551, construct 552 the unique client UCP 23 by         executing the client transformer CPT 22 in the manner described         in Table 13.     -   Instead of executing the original program, execute 553 the         constructed unique client UCP 23.

It is an advantageous aspect of the present invention that any of the three embodiments of the present invention described above in FIG. 13, in FIGS. 14 and 15, and in FIGS. 16 and 17, and/or other embodiments of the client program transformer CPT 22, can be combined with any of several possible embodiments of the service interface transformer SIT 25 and/or with any of several possible embodiments of the function UVOC.

In another variation on the above embodiments of the client program transformer CPT 22, the function UVOC is used differently. Each substitution code comprises the result of running the function UVOC with the input being the constant to be replaced (instead of comprising a call to the function UVOC with the input being the constant to be replaced). In other words, for a given constant C, the substitution code is a different constant C2 computed by executing UVOC with the constant C as input. In this “direct replacement” approach, the “mapping table” of the function UVOC (described below) is created by the client program transformer's CPT 22 use of UVOC. The resulting “mapping table” is then used by the service interface transformer SIT 25 (described below) which embeds the “mapping table” data into the interceptor INTC 26 (described below) for use by the function COVU (described below).

The purpose of the function UVOC is to translate its input data from an expression in the standard linguistic interface SLI 31 of the service to an expression in the unique variant ULI 33. When a unique client program UCP 23 executes, part of its processing comprises assembling one or more units of data into an expression for passing to the interpreter. The data units comprise constant data (part of the program itself) and/or variable data, that is, data that the program obtains during execution, for example, from an input dataset. The result of such processing yields an expression in the unique variant ULI 33 if and only if the resulting expression is a sequence of units comprising one of (a) data returned from a call to UVOC, (b) data that represents constant data in the standard language SLI 31, or (c) data that represents lexical “white space” in the standard language SLI 31. That is, a valid expression of the unique variant ULI 33 can be constructed by a program UCP 23 using variable data, so long as every variable data value is limited to a representation of a constant value in the standard language. Otherwise, an expression is not a valid expression of ULI 33 because it includes inadmissible data (possibly but not necessarily including fragments of the standard language SLI 31). This is to allow partitioning an input string so as to enable distinguishing between SLI 31 data and ULI 33 data.

FIG. 18 is a flow diagram illustrating the steps of operation of the function UVOC, according to one embodiment of the present invention. In FIG. 18, the term “mapping table” refers to state data comprising a table which maps arbitrary strings to randomly generated strings, the table having two columns and a growing number of rows; the term “special characters” refers to characters that are not part of the legal lexical structure of the standard language SLI 31; the term “unique number” refers to a number obtained by executing a pseudo-random number generator or similar source of numbers with the property that there is a very low likelihood that any two generated numbers will be the same.

-   -   Lookup 560 the input string in the first column of the “mapping         table.”     -   If the input string is not found 561, create 562 a new row in         the “mapping table.” The first column of the new row is the         input string. The second column is a new “mapping string” that         begins with a “special character” and is otherwise composed of         the sequence of digits of a “unique number” together with zero         or more “special characters” interspersed among the digits.         -   The special characters may be interspersed among the digits             according to any deterministic mixing scheme. For example,             if the sharp-sign/pound-sign character is not part of SLI 31             then one example would be #12345 while others would be             ##1##2##3##4##5## or, in the case where curly braces are not             part of SLI 31, {12345} or }1}2}345.     -   Return 564 the string in the second column of the row that         contains the input string in the first column.

It will be observed that every return value from the function UVOC, as specified above, is a string that is not part of SLI 31 because of the use of the “special characters”. In an alternative embodiment of the present invention, a UVOC return value may be a string representing constant data in SLI 31 so long as subsequent re-translation distinguishes between (a) constants in SLI 31 that were returned from a call to UVOC, and (b) constants in SLI 31 that were not returned from a call to UVOC.

In an alternative embodiment of the present invention, a new table item is created for each input string, regardless of whether the input has been seen by a previous invocation of UVOC. In both of these embodiments, the unique language is unique (with respect to other unique variants of standard language SLI 31) partly by virtue of the fact that a distinct “unique number” is used in the formulation of each distinct lexical element of the unique language ULI 33. In an alternative embodiment, a unique number is obtained only the first time the UVOC function is called within the unique client program UCP 23, with each new table entry being a distinct derivative of the same unique number, e.g. the unique number followed by the value of a counter incremented for each new table entry.

In the above-described embodiments of the function UVOC, the mapping table is constructed at run-time during a call to UVOC.

In an alternative embodiment, the client transformer CPT 22 adds in the code of the unique client program UCP 23 some additional software which (a) executes during the initialization of the program UCP 23 before a call to UVOC, and (b) generates the mapping table for UVOC. Subsequent calls to UVOC use this pre-built table for lookup of input, in order to return the second element in a table entry that matches the input.

It is an advantageous aspect of the above embodiments that the generation of the unique language ULI 33 occurs when the program UCP 23 executes, and hence does not depend on secrecy of the definition of ULI 33 that is persistent, depending on stored data, etc. Further, each time a given program UCP 23 executes, a different language ULI 33 is generated.

In an alternative embodiment of the present invention, the mapping table is built during the “build phase”. The client transformer CPT 22 adds in the data of the unique client program UCP 23 additional data representing a pre-built mapping table. When UCP 23 executes, calls to UVOC use this pre-built table for lookup of input, in order to return the second element in a table entry that matches that input.

In the above-described embodiments of the function UVOC, there is a direct mapping from an input string to a syntactic element of the language ULI 33. That is, each language ULI 33 has no correlation to the syntax of the standard language SLI 31. Rather, the syntax of each language ULI 33 is based on the fragments of the standard language SLI 31 that are embedded in programs CP 21 and their derivative programs UCP 23. Each of these fragments is mapped in an entry in the table for the function UVOC.

In an alternative embodiment of the function UVOC, the syntax of each language ULI 33 is the same as syntax of the standard language SLI 31. The grammar of each language ULI 33 differs from the grammar of the standard language SLI 31 only in the spelling of the keywords. Each language ULI 33 has a unique set of keywords. For example, for a constant value “ELSE IF” representing a fragment of the standard language SLI 31, an earlier embodiment of UVOC might, if given “ELSE IF” as input, return “#12345”, whereas the present embodiment of UVOC might return “#12345 #23456” (having the two lexical elements “#12345” and “#23456” separated by white space) with the critical difference that there is one lexical element in the output string for each lexical element in the input string. This substitution per lexical unit applies to keywords of the standard language SLI 31, but in some embodiments may extend to other lexical elements as well. The present embodiment of UVOC may be used in conjunction with any of the earlier embodiments, e.g. in terms of when the “mapping table” is built, how the “unique number” is generated and used, and/or any of the embodiments described above.

In an alternative embodiment of the function UVOC, the syntax of each language ULI 33 can be determined not by the syntax of the standard language SLI 31, nor by a one-to-one mapping between UVOC inputs and outputs, but rather by any repeatable method for determining how to divide a UVOC input into substrings, and having the UVOC output comprise a “mapping string” for each substring.

The interceptor INTC 26 depends on a function COVU that is the inverse of the function UVOC. COVU shares the “mapping table” with UVOC, i.e. uses the same state data that UVOC uses and updates. FIG. 19 is a flow diagram illustrating the steps of operation of the function COVU, according to an embodiment of the present invention:

-   -   Lookup 570 the input string in the second column of the “mapping         table.”     -   If input string is not found 571, create 572 a new row in the         “mapping table.” The second column of the new row is the input         string. The first column is a new “mapping string” as defined in         the above description of FIG. 18.     -   Return 573 the string in the first column of the row that         contains the input string in the second column.

It will readily be seen that UVOC translates a fragment of a standard language SLI 31 to a unit of a unique linguistic interface ULI 33, and COVU translates that same unit back to the same fragment. Furthermore, if COVU's input string is not a unit of the unique linguistic interface ULI 33 (i.e. COVU's input string is not found in the second column of any row of the mapping table), then COVU translates that input to a new unit of the unique linguistic interface ULI 33.

The purpose of the service interface transformer SIT 25 is to generate and install the interceptor INTC 26. Different embodiments of the present invention accomplish this in different ways. In one embodiment, the service interface transformer SIT 25 modifies a software implementation of the service SVC 24, such that the interceptor INTC 26 software receives service requests and preprocesses them before calling on the pre-existing service SVC 24 software to process the request that results from the interceptor's INTC 26 pre-processing. In other embodiments, the service SVC 24 is not modified, and the interceptor INTC 26 is installed in the network and/or system-local communication path between the service SVC 24 and one or more clients of the service SVC 24. In another embodiment, the service interface transformer SIT 25 replaces the service SVC 24 entirely with a new implementation having no interceptor per se but rather implementing one or more unique linguistic interfaces ULI 33 used by unique client programs UCP 23.

In one embodiment, an instance of the service interface transformer SIT 25 works with the client transformer CPT 22 to include in unique programs UCP 23 software implementing an interceptor INTC 26 which pre-processes client requests; other means are used to control communication to the service SVC 24 in order to limit effective communication to only unique client programs UCP 23, for example: (a) removing all standard (untransformed) clients from those hosts which have a unique client program UCP 23 installed, and (b) if service resides on a remote host, using network access control to ensure that the only hosts allowed to communicate with the service over the network are such hosts as in (a). In both cases, containment is ensured by preventing subsequent installation of other programs to the hosts.

The interceptor INTC 26 pre-processes requests to a particular service SVC 24 and forwards to the service SVC 24 the result of the pre-processing, wherein the pre-processing determines whether the request is specified in the proper unique linguistic interface ULI 33, and if so re-translates the request (if needed) from a unique linguistic interface ULI 33 to the standard linguistic interface SLI 31.

FIG. 20 is a flow diagram illustrating the steps performed by the interceptor INTC 26, according to an embodiment of the present invention. Not included in FIG. 20 are configuration steps and initialization steps, which may comprise (but are not limited to) defining a desired error handling behavior and a desired translation behavior.

-   -   Scan 580 the input string from beginning to end, performing the         following functions:         -   Identify the legal substrings, which are either:             -   Strings that represent constants as defined in the                 standard language SLI 31.             -   Strings that are a “mapping string” as defined in Table                 18.             -   Strings that are between any two of the above two types                 of legal substrings, or which are at the beginning or                 end of the input string, and that consist entirely of                 “white space” as defined in the standard language SLI                 31.         -   If the input string contains any data that is not a legal             substring, and hence “illegal data” then             -   Identify as an “illegal substring” each sequence of                 illegal data that is between two legal substrings or                 that is before the first legal substring or after the                 last legal substring.             -   Optionally, coalesce into a single illegal substring                 each sequence of substrings that is a sequence of                 illegal substrings and white-space substrings, wherein                 the coalesced illegal substring contains the data of                 each of the illegal substrings and the white-space                 substrings.     -   For all illegal substrings, if any, perform 581 the         error-handling functions currently defined, which may include         logging and alerting, and one of several         illegal-string-processing functions, which may include:         -   Replace the illegal string by converting it into a constant             string value in the standard language SLI 31. (For example,             in some languages, the conversion would be accomplished by             prepending a quotation mark to the string, and appending a             quotation mark to the string.)         -   Replace the illegal string by converting into several             constant values as defined by the lexical structure of the             standard language SLI 31.         -   Call the function COVU on the illegal string, and replace             the illegal string with the string returned from the             function COVU.         -   Remove the illegal string.         -   Leave the illegal string unchanged.     -   For all legal substrings that are “mapping strings”, if any,         perform 582 the translation functions currently defined, which         may include:         -   Leave the “mapping string” unchanged.         -   Call the function COVU on the “mapping string”, and replace             the “mapping string” with the string returned from the             function COVU.     -   If the input string comprises 583 any illegal data, and if the         current error handling behavior specifies 584 the suppression of         erroneous requests, then return 585 the empty string as the         output string.     -   Otherwise 586, 587, return 588 as the output string the result         of making the above replacements (if any) in the input string.

Note that although the processing of the interceptor INTC 26 is described in terms of processing an input string, binary representations of a unique linguistic interface ULI 33 are encompassed by the present invention; in cases of binary representations, the interceptor INTC 26 begins processing with a conversion from binary to string form, or parses the binary representation to find individual lexical elements as defined in the above description of FIG. 19.

Note that several different outputs are possible depending on the configuration of desired error-handling and translation functions. Some examples are as follows:

-   -   In one embodiment of the service interface transformer SIT 25,         the service SVC 24 is modified to implement only one or more         unique linguistic interfaces ULI 33; in this case, the desired         behavior comprises: leaving legal substrings unchanged,         returning an error for requests that contain illegal data,         and/or other such action.     -   In another embodiment of the service interface transformer SIT         25, the desired behavior comprises: re-translating (via the         function COVU) the mapping strings back to their original value         in the standard language SLI 31, converting illegal strings into         constant values of the standard language SLI 31, and passing the         resulting output string to the interpreter of the standard         language SLI 31.     -   In another embodiment of the service interface transformer SIT         25, the desired behavior comprises: re-translating (via the         function COVU) the mapping strings back to their original value         in the standard language SLI 31, translating illegal strings         (via the function COVU) into units of the unique language ULI         33, and passing the resulting output string to the interpreter         of the standard language SLI 31. Since units of ULI 33 violate         the lexical structure of SLI 31, the request will fail as the         interpreter rejects the input string as invalid.     -   Another embodiment of the service interface transformer SIT 25         comprises a “transparent mode”, wherein mapping strings are         re-translated but illegal strings are left alone, thereby         generating a request that would have been produced by a standard         client CP 21.     -   Another embodiment of the service interface transformer SIT 25         comprises a “null mode”, wherein no modification is performed.         Optionally, this is combined with a UVOC setting wherein the         UVOC returns the input as output (i.e. performs a “no-op”), the         combination generating a service request that would have been         produced by a standard client CP 21.     -   Another embodiment of the service interface transformer SIT 25         comprises a “test mode”, combining the “transparent mode” with         the logging of illegal data. In cases where the client and         server are being tested with test data known not to include         truly illegal data (i.e. illegal data comprising input         originating from outside the client program, as opposed to         illegal data originating from client and simply due to improper         CPT 22 operation), the logging will identify fragments of the         standard language resulting from incomplete or erroneous         operation of the client program transformer CPT 22 or the         function UVOC. Using an input set known not to comprise such         truly illegal data helps to identify other illegal data (if any)         for testing the effectiveness of CPT 22.

It is an advantageous aspect of the present invention that the combination of the operation of the function UVOC in the unique client UCP 23 together with the operation of the function COVU in the interceptor INTC 26 can be used to defeat a class of usage known as “code insertion attacks”. In a code insertion attack, while the expected usage of an application comprises external input limited to constant data, the external input may nevertheless comprise data representing code to be executed when passed to the interpreter of a service, wherein the service is used by the application and has a linguistic interface. In contrast, in the present invention only legitimate standard language fragments pass through the function UVOC and hence through the interceptor INTC 26, while standard language fragments in user input are removed or converted (to constant data or to erroneous input defined in a unique language) so as to prevent interpretation.

It is noted that a form of virtualization is implemented when the desired translation behavior is to re-translate via COVU, and the desired error behavior is to translate via COVU. In this usage, all input to the service (except for constant values of the service's standard language) is subject to transformation via the function COVU's use of the “mapping table.” For any data sent from a unique client program to the interpreter of a standard language, the only data that will be correctly processed by the standard language interface comprises data previously translated by UVOC and then re-translated by COVU to the standard language. Data that has not been previously translated will be translated by COVU to a unique-language unit representing illegal input for the standard language interpreter. The “mapping table” for a unique client UCP 23 is analogous in operation to an operating system's virtual memory map for a process. Just as memory references are unavoidably mapped to avoid direct addressing and to generate errors for unmapped addresses, all language interface data are unavoidably mapped to prevent direct interface usage and to generate errors for invalid usage. A process can access the physical memory that has been specifically allocated for it; and analogously a program can use specific expressions in the standard language that have been specifically prepared for use via UVOC. The code that performs the mapping in both cases does not examine or interpret the data mapped, and there is no computation to determine a judgment of legitimacy of data or a decision about authorization of usage.

Foregoing described embodiments of the invention are provided as illustrations and descriptions. They are not intended to limit the invention to precise form described. In particular, it is contemplated that functional implementation of invention described herein may be implemented equivalently in hardware, software, firmware, and/or other available functional components or building blocks, and that networks may be wired, wireless, or a combination of wired and wireless. Other variations and embodiments are possible in light of above teachings, and it is thus intended that the scope of invention not be limited by this Detailed Description, but rather by Claims following. 

1-51. (canceled)
 52. A method, comprising: defining a manifest of one or more client programs, the one or more client programs authorized to use a service; and storing the manifest for subsequent reference by a client program execution procedure, wherein the client program execution procedure generates a second client program based on the first client program and a substitution code, and wherein the client program execution procedure executes the second client program.
 53. The method of claim 52, wherein the manifest comprises a manifest integrity data, the client program execution procedure evaluating the manifest integrity data to detect a modification to the manifest.
 54. The method of claim 53, wherein the client execution procedure computes a new integrity data for the manifest, wherein if the manifest integrity data does match the new integrity data then execution of all client programs identified in the manifest is blocked.
 55. The method of claim 52, wherein the manifest comprises a program integrity data for a first client program of the one or more client programs identified in the manifest, the client program execution procedure evaluating the program integrity data to detect a modification to the first client program.
 56. The method of claim 55, wherein the client execution procedure computes a new program integrity data for the first client program, wherein if the program integrity data does match the new program integrity data then execution of the first client program is blocked.
 57. The method of claim 52, wherein the manifest comprises a substitution code for replacing a first constant data in a first client program of the one or more client programs, the first constant data expressed in a first grammar type directed to a first linguistic interface of a first service implementation, the substitution code indicating an expression in a second grammar type directed to a second linguistic interface of a second service implementation, the expression equivalent to the first constant data; wherein the first and second service implementations implement equivalent services, and the first and second linguistic interfaces are distinct.
 58. The method of claim 57, wherein the substitution code comprises a second constant data.
 59. The method of claim 57, wherein the substitution code comprises a subroutine call having the first constant data as an argument, wherein the subroutine call returns a second constant data as the expression in the second grammar type directed to the second linguistic interface.
 60. A method, comprising: identifying a first substring in an input string in a first client program, the first substring and the input string directed to a first linguistic interface of a first service implementation; and replacing the first substring with a second substring, the second substring directed to a second linguistic interface of a second service implementation; wherein the first and second service implementations implement equivalent services, and the first and second linguistic interfaces are distinct.
 61. The method of claim 60, wherein the second substring is computed by calling a function using the first substring as input for the function.
 62. The method of claim 60, wherein the replacing the first substring includes: searching a mapping table having a plurality of arbitrary strings corresponding respectively to a plurality of mapping strings; and identifying a mapping string of the plurality of mapping strings as the second substring, the mapping string corresponding to an arbitrary string of the plurality of arbitrary strings, wherein the arbitrary string matches the first substring.
 63. The method of claim 62, wherein the new mapping string comprises a unique number representing the first substring.
 64. The method of claim 62, wherein the new mapping string comprises one or more special characters, and wherein the one or more special characters are not included in a first grammar type of the first linguistic interface.
 65. The method of claim 60, wherein the replacing the first substring includes: searching a mapping table having a plurality of arbitrary strings corresponding respectively to a plurality of mapping strings; and creating a new entry in the mapping table if none of the arbitrary strings of the plurality of arbitrary strings matches the first substring, wherein the new entry includes a new arbitrary string matching the first substring, and wherein a new matching string is generated to correspond to the new arbitrary string.
 66. The method of claim 65, wherein the new mapping string comprises a unique number representing the first substring.
 67. The method of claim 65, wherein the new mapping string comprises one or more special characters, wherein the one or more special characters are not included in a first grammar type of the first linguistic interface.
 68. The method of claim 60, wherein the first substring includes the first client program in its entirety.
 69. A method, comprising: calling a subroutine and providing a first constant data as an argument for the subroutine, the first constant data directed to a first linguistic interface configured to interpret requests that conform to a first grammar type; receiving a second constant data as a return value from the subroutine, the second constant data directed to a second linguistic interface configured to interpret requests that conform to a second grammar type that is different than the first grammar type; and sending a service request to a modified service implementation having the second linguistic interface, the service request comprising the second constant data; wherein the modified service implementation is equivalent to an original service implementation having the first linguistic interface, and wherein the second constant data is equivalent to the first constant data.
 70. The method of claim 69, wherein the second constant data is a mapping string corresponding to the first constant data.
 71. The method of claim 70, wherein the mapping string comprises one or more special characters, wherein the one or more special characters are not included in the first grammar type of the first linguistic interface. 